The Arsenal Files 8

home *** CD-ROM | disk | FTP | other *** search

/ The Arsenal Files 8 / The Arsenal Files Collection #8 (Arsenal Computer) (1996).ISO / pcboard / pcbfv40.zip / PCBFV.DOC < prev next >

Wrap

Text File | 1996-11-14 | 71KB | 1,498 lines

------------------------------------------------------------------ | | | | | | | | | PCBFV Version 4.0 | | | | PCBoard F V Compressed File Viewer | | | | For | | | | PCBoard Versions 15.x | | | | including | | | | PCBoard /M Multi-Port | | | | | | * Seamless Interface - Looks Like Part of PCBoard * | | | | | | Allows Text File Reading On-Line | | | | | | Allows Selecting Files For Individual Download | | | | | | Runs In The F V Shell, As A Door, In PCBFiler, and Locally | | | | | | | | Highly Sysop-Configurable | | | | | | | | PCBFV Version 4.0 | | | | (C) Copyright 1990-1996 Yandell Custom Software | | | | 9438 U.S. Hwy. 19 N. Suite 212 | | Port Richey, FL 34668 | | | | DATA -- (813) 842-8099 | | | | | | November 14, 1996 | | | | | | | ------------------------------------------------------------------ -------------------------------------------------------------------- PCBFV -------------------------------------------------------------------- TABLE OF CONTENTS INTRODUCTION Page ------------ ---- 1.0 What Is PCBFV 3 1.1 What is New in Version 4.0 (Upgrading) 3 1.2 Definitions - (F)lag, FLAG-File, (FLAG) 3 1.3 Supported Operating Systems and Multi-taskers 4 INSTALLING PCBFV IN THE F_V SHELL --------------------------------- 2.0 Determining Memory Requirements 5 2.1 Setting Up PCBVIEW.BAT 6 2.2 Running FVSETUP and Creating PCBFV.CNF 6 2.3 Running FVSETUP and Editing FVTEXT Files 6 2.4 Multi-Node Systems and PCBFV.CNF 7 2.5 MENU and HELP Files (Macros, Color, Etc.) 8 2.6 RIP Graphics and Files 8 2.7 Limiting (F)lag File Types with FLAG.DAT 9 2.8 Managing Caller Created FLAG-Files 9 INSTALLING PCBFV IN OTHER AREAS ------------------------------- 3.0 Installing PCBFV in PCBFiler 10 3.1 Installing PCBFV as a Local Utility 10 3.2 Installing PCBFV as a Door 11 RUN-TIME CONSIDERATIONS ----------------------- 4.0 Notes Regarding the (R)ead Command 12 4.1 Notes Regarding the (S)elect Command 13 4.2 Notes Regarding the (F)lag Command 13 4.3 Notes Regarding the AutoFlag Feature 14 4.4 Notes Regarding "Flagging Across Files" 15 4.5 Notes Regarding the (I)nventory Command 15 4.6 Notes Regarding the (V)iew Command 15 4.7 Notes Regarding the (D)elete Command 16 4.8 Notes Regarding the (E)xtra Info Command 16 MISCELLANEOUS ------------- 5.0 Required Compression Utilities 17 5.1 New Compression Utility Releases 18 5.2 Sysop Function Keys 18 5.3 Technical Notes 19 5.4 Error Messages and Solutions 20 5.5 Caller Log Entries 21 5.6 Where to Receive Assistance 21 5.7 Disclaimer and Warranty 22 5.8 License to use PCBFV 22 REGISTRATION ------------ 6.0 Registering PCBFV 23 6.1 Register with CONFIDENCE - Author Information 23 -------------------------------------------------------------------- Page 3 PCBFV Page 3 -------------------------------------------------------------------- 1.0 What is PCBFV ------------------ PCBFV is a PCBoard BBS utility primarily for use in the F V (File View) shell process. PCBFV may also be used as the file viewer in PCBFiler. PCBFV may be installed to run as a door. PCBFV displays the contents of ZIP, ARJ, RAR, LZH, and ARC files. Self-extracting files created by PKZIP, RAR, LHA, and ARJ are supported. PCBFV will also display the resolution of .GIF files (width-height-colors). PCBFV will optionally allow a caller to (R)ead text files contained within a compressed file, and search for text within those files. The Sysop may allow the caller to read non-text files in a HEX mode display. PCBFV will also optionally allow a caller to (F)lag a compressed file's members for individual downloading. Uncompressed files in a download path may be read by PCBFV. The Sysop has full control over which features of PCBFV are enabled on their system. The goal in PCBFV's development has been to make the caller's interface to the F V process appear as "seamless" as possible. Great emphasis has been placed on making the appearance of PCBFV appear as similar as possible to PCBoard. 1.1 What is New in Version 4.0 (Upgrading) ------------------------------------------- Read the enclosed FEATURES.NEW file for a list of new features in PCBFV version 4.0. REGISTERED USERS of PCBFV prior to version 4.0: PCBFV 4.0 requires a new registration number. If you registered PCBFV more 1 (one) year prior to the release of PCBFV 4.0 (11/14/96), then an upgrade fee is required. See UPGRADE.DOC for instructions and more information. 1.2 Definitions - (F)lag, FLAG-File, (FLAG) -------------------------------------------- The following are definitions of similar words used in PCBFV: (F)lag: This represents the "F" command. A caller may (F)lag a file inside a compressed file for separate download if the Sysop allows this activity (configured with FVSETUP.EXE). FLAG-File: This term represents the compressed file (FLAG.ZIP) which will be created with the (F)lag command. (FLAG): If "FLAG" is entered at the PCBFV main prompt, the entire compressed file being viewed will be entered into PCBoard's FLAG queue upon return to PCBoard. Since the "FLAG" command requires no setup or configuration all references to (F)lag, Flag, Flagging etc. in this documentation are references to the (F)lag command process. -------------------------------------------------------------------- Page 4 PCBFV Page 4 -------------------------------------------------------------------- 1.3 Supported Operating Systems and Multi-taskers -------------------------------------------------- PCBFV is a DOS application which has been designed with file-sharing and "multi-tasker" friendliness in mind. PCBFV is OS/2, DESQview and Windows aware. These operating systems are automatically detected, and time slices are given back to the multi-tasker while PCBFV is idle (waiting at an input prompt). If desired, you may disable PCBFV's "time-slice-return" capability by setting the appropriate parameter in FVSETUP. PCBoard for OS/2 and PCBoard /M multi-port software are supported by PCBFV through the FOSSIL interface. PCBFV reads PCBOARD.DAT on the node where it is running and automatically determines if PCBoard has been set for FOSSIL or OS/2 use on that node. If it is, PCBFV will automatically use FOSSIL mode, and a FOSSIL driver must be present and properly installed for PCBFV to function properly. A FOSSIL driver is required if using PCBFV with "PCBoard for OS/2". An OS/2 communications driver often used by PCBoard Sysops is SIO. Many people incorrectly assume SIO by itself is a FOSSIL driver, but it is not. The SIO package -contains- a FOSSIL driver called VX00 which must also be installed with SIO. If a single PCBOARD.DAT is used on a multi-node system, PCBFV must be able to read the PCBDAT environment variable so that it knows where the single copy of PCBOARD.DAT can be found. Likewise, PCBFV must also be able to read the PCB environment variable to determine if /PORT: /OS /FOSSIL etc. overrides exist for the node. The PCBoard manual contains instructions for setting these environment variables when using third-party DOS applications with "PCBoard for OS/2" Consult the PCBoard manual for configuring non-DOS platforms of PCBoard for use with third-party DOS applications. Also consult your FOSSIL driver documentation for proper installation. A discussion of these topics here exceeds the scope of the PCBFV documentation. -------------------------------------------------------------------- Page 5 PCBFV Page 5 -------------------------------------------------------------------- 2.0 Determining Memory Requirements ------------------------------------ PCBoard MUST be set to "Swap Out During Shell" for proper operation. To Insure that you have PCBoard set properly: (1) Run PCBSETUP.EXE. (2) Select "(G) Configuration Options" (3) Select "(D) Configuration Switches" (4) Answer "Swap Out During Shell" with a "Y" for YES. (5) Save the changes and repeat steps 1 through 4 for all nodes. PCBFV can also swap itself to EMS or disk if there is insufficient memory to call upon an external compression utilities. Since PCBoard will already be swapped from memory, it is very unlikely PCBFV would ever need to swap. The following is a loose guide-line to determine if PCBFV's swap capabilities should be utilized. ZIP: 80K, 10K if (F)lagging from ZIP files to FLAG.ZIP. ZIP: 80K, 195K if (F)lagging from NON-ZIP files to FLAG.ZIP. ARJ: 220K, 315K if (F)lagging to FLAG.ARJ. RAR: 165K, 425K if (F)lagging to FLAG.RAR. LZH: 155K, 200K if (F)lagging to FLAG.LZH. ARC: 105K, 140K if (F)lagging to FLAG.ARC. Note the extremely low memory requirement for flagging a member from a ZIP file to a FLAG.ZIP file. This is because PCBFV actually copies the already compressed member file to the FLAG.ZIP file, then PCBFV reconstructs the appropriate ZIP information in the new FLAG.ZIP. If a member of a non-ZIP file is flagged -from-, PCBFV will use the appropriate utility (ARJ, RAR etc.) to extract the file, then use PKZIP.EXE to compress the file to FLAG.ZIP. DO I SWAP PCBFV? ---------------- If you enable "(F)lag member files for separate download", pick the amount of "K" memory from the right-hand column above for the type of FLAG-File you defined in FVSETUP (ZIP, ARJ etc.). Then proceed down the left-hand column above of "K" memory. Select the highest amount of "K" memory for the types of compressed files you permit on your system. The higher of these two amounts is the minimum "K" amount that needs to be shown in the red box on PCBFV's status-line. If the status line shows less, you need to turn PCBFV's swapping on by setting the appropriate parameter in FVSETUP.EXE. In most cases, swapping PCBFV will never be needed. If RAR is used for the FLAG-File, swapping will probably be required BUT still may not yield enough memory. For this reason, (F)lagging -to- an RAR file is excluded from the PCBFV warranty described in this manual. -------------------------------------------------------------------- Page 6 PCBFV Page 6 -------------------------------------------------------------------- 2.1 Setting up PCBVIEW.BAT --------------------------- Load PCBVIEW.BAT into a text editor. The syntax for calling PCBFV is out-lined below. NOTE: Never change drives or CD\ in PCBVIEW.BAT. ALWAYS call PCBFV with its location in-line as shown below. C:\PCBFV\PCBFV.EXE PCBFV.CNF %1 ------------------ --------- -- | | |-> PCBoard will replace this with | | the compressed file's name. | | | ---------> The name of the configuration | file. Enter a file NAME only. | NEVER place a location with name. | -------> The executable file name. You MUST place its location in-line as shown above if you are not putting PCBFV.EXE in each node's \PCB root. 2.2 Running FVSETUP and Creating PCBFV.CNF ------------------------------------------- Enclosed with PCBFV 4.0 is a file called FVSETUP.EXE. This file allows you to easily and quickly configure your PCBFV configuration files. Use the PCBFV.CNF file name when starting FVSETUP then modify the defaults to suit your needs. IMPORTANT: Press F1 at each FVSETUP parameter for ON-SCREEN HELP. To start FVSETUP.EXE, enter FVSETUP at the DOS prompt. FVSETUP will ask which configuration file name to use. PCBFV.CNF will be the most appropriate configuration file name. 2.3 Running FVSETUP and Editing FVTEXT Multi-Language Files ------------------------------------------------------------ To make alternative FVTEXT files, use the DOS COPY command to create a new file, for instance: COPY FVTEXT FVTEXT.FRE (.FRE is a common extension given to FRENCH language files). Then use FVSETUP.EXE to edit and change the text in FVTEXT to suit your needs. PCBFV detects the language in use and uses the language version of FVTEXT. If the default language is used or the appropriate language version of FVTEXT does not exist, the default FVTEXT file without an extension will be used. PCBFV replaces the ~ character with hard spaces in the same fashion PCBoard does with PCBTEXT language files. PCBFV does not support %FILENAME conventions in any of the FVTEXT parameters. -------------------------------------------------------------------- Page 7 PCBFV Page 7 -------------------------------------------------------------------- 2.4 Multi-Node systems and PCBFV.CNF ------------------------------------- To use a single PCBFV.CNF (providing you are using one PCBFV.EXE) for all nodes, use the @NODE@ macro in these FVSETUP parameters: * Work location of extracted file --------------------------------- This is a "work" location of extracted files for both the (R)ead and (F)lag commands. Whenever a caller (R)eads or (F)lags a file, that file is extracted to the location specified here. If you have a lot of RAM drive space, it is ideal for this location. On a multi-node system, you MUST specify a different "work" directory for each node and indicate that node's directory here. If you are multi-node and using a single PCBFV.CNF, place the @NODE@ macro in-line here: C:\WORK@NODE@\ PCBFV will replace @NODE@ internally based on the node information from PCBoard. For example, on node #1 the actual directory on your drive would be: C:\WORK1\ PCBFV never deletes work directories. It will insure the appropriate work directory exists each time it is run, and creates it if not. If you nest your work subdirectories, PCBFV will only try to create the "last" directory in the nest. For example, if your work location is C:\PCB\PCBFV\WORK then PCBFV would only try to create \WORK. If the C:\PCB\PCBFV directory doesn't already exist, PCBFV will not be able to create C:\PCB\PCBFV\WORK. * Loc\Name of New (F)lagged File -------------------------------- If (F)lag is allowed, enter the location AND name of the file which will be created and will contain the individual files the caller picks for downloading. The location MUST be a drive & path which are listed in your DLPATH.LST! The extension (.ZIP .ARJ) you give the filename will determine the compression method used by PCBFV to create the file. In a MULTI-NODE environment, the file NAME in the above parameter MUST be different for each of the nodes. You may accomplish this by either placing a different name in each node's .CNF file, or if you are using a single PCBFV.CNF then place the @NODE@ macro in-line here, such as: C:\UPLOAD\FLAG@NODE@.ZIP PCBFV will replace @NODE@ internally based on the node information from PCBoard. For example, on node #1 the actual file name created would be: C:\UPLOAD\FLAG1.ZIP IMPORTANT: The location specified here MUST be in DLPATH.LST, and should NOT be located in a PCBoard INDEX file. -------------------------------------------------------------------- Page 8 PCBFV Page 8 -------------------------------------------------------------------- 2.5 MENU and HELP Files (macros, color, etc.) ---------------------------------------------- Color is used in MENU and HELP files by utilizing the same color macros used in PCBoard. ANSI capabilities ("G" type files) have been intentionally omitted. Language, security, and RIP versions of MENU and HELP are supported. Review MENU and HELP and remove any commands which are not enabled. MENU and HELP files must reside in the same location with PCBFV.EXE. There are four very important @macros@ used in the HELP file and may be used in MENU files if desired: @FILENAME@ - Whenever this appears in HELP, PCBFV will replace it with the file name which is currently being viewed. @FILENAMEPD@ - Same as @FILENAME@, except padded to twelve spaces. @FLAGFILE@ - Whenever this appears in HELP, PCBFV will replace it with the name of the compressed file which will be created when a caller (F)lags files for separate download. This feature is very helpful for multi-node systems, since a different compressed file name is mandatory for each node. @FLAGFILE@ will be replaced by that node's file name as it appears in that node's .CNF file, thereby creating the need for only one help file. @FLAGFILEPD@ - Same as @FLAGFILE@, except padded to twelve spaces. 2.6 RIP Graphics and Files --------------------------- PCBFV supports RIP graphics through the use of three files: MENUR - This is the RIP version of the menu file. READR - This appears at the "More?" prompt while (R)eading a text file extracted from a compressed file. Non-RIP versions of this file are not used by PCBFV. SPACR - This appears at the "SPACE to Mark" prompt while (L)isting the contents of a compressed file. Non-RIP versions of this file are not used by PCBFV. These files have been designed so that a caller needs to only use their mouse for all PCBFV functions. In RIP mode, it is assumed these three files are present and properly constructed. PCBFV uses "hot-keys" in RIP mode, so if modifying these files, do not add a "carriage-return" command to "button-clicks". To disable RIP mode in PCBFV, remove all MENUR file(s). -------------------------------------------------------------------- Page 9 PCBFV Page 9 -------------------------------------------------------------------- 2.7 Limiting (F)lag File Types With FLAG.DAT --------------------------------------------- You may limit (F)lagging activity to certain types of files. With a text editor, create a file called FLAG.DAT in the same location with PCBFV.EXE. Simply begin entering COMPLETE or WILDCARD file names of file types which you wish the caller to be able to (F)lag. Press enter (RETURN) after each name so that each entry is on a new line. If FLAG.DAT is not present, no limitations will be placed on (F)lag names. See figure 2.7 below for valid examples of file names. ------------------------------------------------------------------ | Good examples Bad examples | | ------------- ------------ | | *.DOC PCBFV uses regular DOS .DOC | | *.TXT wildcard specs to see if .TXT | | READ*.* a file is a match. If so, READ | | *.NEW the file may be (F)lagged. .NEW | | FILE.CFG FILE* | ------------------------------------------------------------------ ---- Figure 2.7 ---- If the caller attempts to (F)lag a file which is not permitted, they will be shown the types of file names which can be (F)lagged. FLAG.DAT must reside in the same location with PCBFV.EXE 2.8 Managing Caller Created FLAG-Files --------------------------------------- Each time PCBFV runs it checks for the presence of a caller created FLAG-File. If the file exists and the Sysop has DISABLED the "Flag across files" function, the file will be deleted. If "Flag across files" is allowed, an information file (created by PCBFV, explained in detail in section 4.5 page 15) is checked to see if the same caller executing the view is the same caller who created the current FLAG-File. If so, the FLAG-File will be kept for additional flagging, if not, the caller created FLAG-File is deleted. Create or modify $$LOGOFF.BAT in a path available to all nodes or in each node's root to include: if exist c:\down\flag.zip del c:\down\flag.zip Replace "c:\down\flag.zip" with YOUR location and file name. If you run a multi-node system, you can use the PCBNODE environment variable in the batch file as follows: if exist c:\down\flag%PCBNODE%.zip del c:\down\flag%PCBNODE%.zip %PCBNODE% will be replaced by the actual node number. -------------------------------------------------------------------- Page 10 PCBFV Page 10 -------------------------------------------------------------------- 3.0 Installing PCBFV in PCBFiler --------------------------------- Enclosed with PCBFV version 4.0 is a utility called FVMM, which is designed to bring many capabilities to PCBFiler's ALT-V process that have not been available before. Review FVMM.DOC. If you decide you do not want to install FVMM in PCBFiler, the instructions below will assist you in installing PCBFV in PCBFiler instead. A /L parameter is used (see below) which instructs PCBFV to operate in a "true" local mode. All "on-line" functions are disabled, such as keyboard time-out, caller status line at the bottom of the screen, etc. The local monitor type is automatically detected and color is used if appropriate. Special Note: If you are installing PCBFV in PCBFiler and are using PCBFV.CNF files with the @NODE@ macro in the "work location of extracted file" parameter in FVSETUP, you must create a special configuration file for use in the /L mode which fully specifies the "work location". You may call this file FILER.CNF and install it with PCBFV into PCBFiler as shown below. At PCBFiler's first screen select "Edit PCBFILER defaults page 2". At the bottom of this screen, enter parameters as follow: File VIEWERS - filename extensions and commands for executing viewer File Extension : ZIP DOS Command : c:\pcb\PCBFV FILER.CNF /L File Extension : ARJ DOS Command : c:\pcb\PCBFV FILER.CNF /L File Extension : GIF DOS Command : c:\pcb\PCBFV FILER.CNF /L For each compression type (which PCBFV is compatible with) place the "DOS Command :" entry as above. The parameters must be placed in the same order as they are shown in the examples: Name\location of PCBFV.EXE, configuration file, then /L. The (S)elect command and all function keys are disabled in this mode. All other sections in this documentation apply to installing PCBFV in PCBFiler. 3.1 Installing PCBFV as a Local Utility ---------------------------------------- Create a batch file called FV.BAT (or whatever name you choose): C:\PCB\PCBFV PCBFV.CNF /L %1 Place FV.BAT (or whatever you name it) in your DOS path, and you have a full powered viewer, extractor at your fingertips at all times by typing FV FILENAME.ZIP (an extension IS required in this mode). All other areas of this manual apply to this installation. Special Note: If you are installing PCBFV as a local utility and are using PCBFV.CNF files with the @NODE@ macro in "work location of extracted file, you must create a special configuration file for use in the /L mode which fully specifies the "work location". It is recommended that this file be called LOCAL.CNF and installed with PCBFV into FV.BAT instead of PCBFV.CNF as shown above. -------------------------------------------------------------------- Page 11 PCBFV Page 11 -------------------------------------------------------------------- 3.2 Installing PCBFV as a Door ------------------------------- This capability exists in case Sysops have a need to diversify the utilization of PCBFV's many features, or in case there is a limited memory situation and PCBoard and PCBFV cannot be allowed to swap. We have heard from many Sysops saying they installed PCBFV as a private DOOR for themselves and\or their Co-Sysops, free of the limitations they wanted PCBFV to impose on regular callers while using the F V (PCBVIEW.BAT) process. The documentation for installing PCBFV as a door is almost the same as installing it in the F V shell. For door installation, simply follow the instructions below INSTEAD of those found in section 2.1. All other sections apply to door installation. Install a door called FV in DOORS.LST file with PCBSETUP. Place this entry at the end of DOORS.LST, as the recommended usage calls for invoking PCBFV as a door by name (FV), rather than the conventional way of placing it in your door menu and calling it by number. Answer Yes to the USERS.SYS parameter if using PCBoard 15.22 or later. You may answer the SHELL question with a "N" or "S" but never use "Y" or "F" in the SHELL parameter when installing PCBFV as a door. Create a door (batch) file called FV : @echo off C:\PCBFV\PCBFV.EXE PCBFV.CNF C:\PCB /DOOR board --------- ------ ----- | | |_ Put PCBFV into door mode | | | |__Location of THIS node's PCB root | |__ PCBFV configuration file. Notice that we didn't change drive and/or cd\ to the PCBFV location. Instead, we called it directly from where FV is run because of PCBFV's ability to do this. This results in faster load time. If, however, you are running multi-nodes and each node is residing on a different drive, you may find it faster to install PCBFV as a door on each node's drive. Make sure your PCBoard menus reflect the FV command instead of F V. PCBFV (as a door) can be passed a filename from the PCBoard command prompt, the same way the F V shell process passes a file, for example "FV TEST.ZIP". This requires no extra installation by the Sysop and is handled automatically by PCBoard and PCBFV. -------------------------------------------------------------------- Page 12 PCBFV Page 12 -------------------------------------------------------------------- 4.0 Notes Regarding the (R)ead Command ----------------------------------------- The caller may read any type of file, depending on how the Sysop has enabled the HEX mode display feature. Typically, files which contain carriage-return and\or line-feed sequences will be regarded as text files by PCBFV. All other files will have to meet the criteria the Sysop has set for the HEX display feature. The (F)ind Text command available while reading text files is a full featured search mechanism. The whole page surrounding the text is displayed with the found text highlighted in the center line of the screen. The "maximum number of lines to display" setting is honored, callers cannot (F)ind past the number of lines the Sysop may have set for this parameter. The (F)ind command is complimented by a (R)epeat Find, which repeats the last Find command performed on the current text. The "maximum number of lines to display" setting is honored, callers cannot (R)epeat past the number of lines the Sysop may have set for this parameter. (T)op of file command which allows the caller to quickly return to the beginning of the file being read. (P)ageUp allows the previous page of text to be displayed. (E)nd allows the caller to quickly move to the end of the text file. (<) and (>) scroll the screen left and right for viewing long lines of text (longer than 79 characters) on the screen. The (F)ind, (R)epeat, (P)ageUp. (<), (>), (T)op and (E) commands appear in the "More" prompt at the end of a full page of text. The (R)epeat command only appears after a (F)ind has been executed. Corresponding cursor movement keys may be used: Home=(T)op End=(E)nd PgUp=(P)ageUp PgDn=[Enter] and left and right arrows = (<) and (>). This requires the caller to enable the "doorway" mode of their terminal program. The (F)ind command is PCBFV's only limited function in unregistered copies. The (F)ind command IS functional in unregistered copies of PCBFV, but only when the Sysop (the name in record #1 of the USERS file) is the person on-line, or when PCBFV is being used in any local mode. PCBFV will read DOS and non-DOS text files. Non-DOS text files are text files which contain line-feeds only, as opposed to DOS files which contain carriage-returns and line-feeds. PCBFV tests text files for characters such as ANSI escape sequences and form feeds. If either are found PCBFV suppresses them before displaying the text. -------------------------------------------------------------------- Page 13 PCBFV Page 13 -------------------------------------------------------------------- 4.1 Notes Regarding the (S)elect Command ----------------------------------------- PCBFV's (S)elect command is completely conference DLPATH.LST aware. The caller will only be able to (S)elect files to view which are available to the conference they are in (or last in, if using PCBFV as a door). PCBFV's (S)elect command is also completely FSEC aware. When a (S)elect request is found, PCBFV checks FSEC to insure the caller has security to view the file. If the file is password protected, PCBFV will also ask the caller the password, and performs this operation in the same manner as PCBoard. PCBFV uses the "Filename EXTENSION for compressed files" entry in PCBSETUP as the default filename extension when performing its own file searches. 4.2 Notes Regarding the (F)lag Command --------------------------------------- The System Administrator/Operator may specify the type of files the caller may flag (see section 2.7 FLAG.DAT). A security level may be attached to this command. Callers may "flag across files" (see section 4.4 below). There is an (I)nventory command, and the inventory information file is automatically included in each caller created file. Files which are (F)lagged for individual download are automatically placed in the compressed file designated for the node the caller is on. The extracted member is then deleted from the work directory. This keeps the amount of disk space PCBFV is requiring down and allows a RAM drive to be used as a work location, which greatly speeds up overall execution of the F V function. Regardless of how PCBFV is installed, the caller will never be able to include ALL of the files from a compressed file into their caller created file. In all cases, the caller at best will be able to include all but ONE file into their FLAG-File. For instance, if you set PCBFV to allow FIVE files for inclusion into the caller created FLAG-File, and the caller is viewing a compressed file with 4 files, the most they will be able to (F)lag of those is 3 of the 4. The theory behind this is the caller should download the actual file rather than (F)lagging each individual file. The download path(s) which contain your FLAG.ZIP (or FLAG1.ZIP or FLAG2.ZIP etc.) should be placed at the beginning of DLPATH.LST so PCBoard's FLAG search occurs as quickly as possible when returning from the F V shell. Do not place this path in a PCBoard INDEX file. -------------------------------------------------------------------- Page 14 PCBFV Page 14 -------------------------------------------------------------------- 4.3 Notes Regarding the AutoFlag Feature ----------------------------------------- If allowed, PCBFV will make PCBoard think the caller has entered instructions to "FLAG" the caller's FLAG-File as part of PCBoard's own "FLAG" list. PCBoard will remind the caller of the existence of the FLAG-File in the "batch" when the caller enters "D" in PCBoard, logs off without downloading their batch list, etc. How it works: For the purposes of this example, we'll say the name of the caller created file in PCBFV is called FLAG.ZIP. PCBFV will use PCBoard's PCBSTUFF.KBD file feature to tell PCBoard to enter: FLAG FLAG.ZIP at the PCBoard prompt after the F V session. Operational notes: If "flagging across files" and AutoFlag are both enabled and it is the first F V session, AutoFlag will occur. On subsequent F V sessions, if the caller (F)lags (in PCBFV) separate files, they will be asked if they've downloaded the FLAG.ZIP yet (since/if you allow flagging across files, PCBFV has no way of knowing). If they answer Yes, PCBFV will AutoFlag again at the end of the current F V session. If they answer No, PCBFV won't perform AutoFlag. If the caller answers No, and they really have downloaded FLAG.ZIP, then AutoFlag won't occur (since they answered No) and the the file will not be placed in PCBoard's FLAG list. Subsequently, if caller answers Yes they downloaded FLAG.ZIP but really didn't, PCBFV will AutoFlag the caller created (FLAG.ZIP) file. Since the caller really didn't download (in this scenario) it will still exist in PCBoard's FLAG batch list, and the caller will receive: (@OPTEXT@) duplicates a file already in the batch! This is record #554 in PCBTEXT. Changing it to something like: (@OPTEXT@) exists in the batch list... is recommended as it sounds less like an error message, and is still informative if the caller DBs or FLAGs a duplicate d/l file from PCBoard. The @optext@ in the above examples is replaced with the appropriate caller created FLAG-File name (FLAG.ZIP, etc.). The download path(s) which contain your FLAG.ZIP (or FLAG1.ZIP or FLAG2.ZIP etc.) should be placed at the beginning of DLPATH.LST so PCBoard's FLAG search occurs as quickly as possible when returning from the F V shell. Do not place this path in a PCBoard INDEX file. -------------------------------------------------------------------- Page 15 PCBFV Page 15 -------------------------------------------------------------------- 4.4 Notes Regarding "Flagging Across Files" -------------------------------------------- If you allow the caller to "flag across files", this means they will be able to view a compressed file, select files from it to download individually, then view another compressed file and select individual files from it, adding all of the individual files to one caller created FLAG-File for downloading. The number which you place in the "# files in each (F)lagged file" parameter in FVSETUP will be observed, even when "flagging across files" is allowed. If a caller should select an individual filename which is identical in two different compressed files, the caller will be given the choice of which one to keep in the "caller created FLAG-File", as obviously a compressed file cannot contain two files with the same name. For systems that enforce download file counts, you need to be aware that if you allow "flagging across files" and you also place a high number in the "# of files in each (F)lagged file" parameter in FVSETUP, unscrupulous callers might be able to use it to "beat the system". In most cases, placing a low number in the FVSETUP field "# of files in each (F)lagged file" will prevent this undesirable effect. Also, using FLAG.DAT (see section 2.7) to limit the types of names of files that can be flagged, in conjunction with a low number allowed in each caller created file, will surely thwart this activity. In all cases, disabling "flagging across files" will eliminate the need for concern completely. 4.5 Notes Regarding the (I)nventory Command -------------------------------------------- This command allows the caller to take inventory of their current FLAG-File. They will be shown the contents which will consist of a list of the individual files they have flagged, the compressed file name which the individual files came from, and the size in bytes of the FLAG-File they have created. The file containing the information shown by the (I) command is created by PCBFV in each node's work directory you have assigned it. This file is also automatically included in the FLAG-File the caller will download, so that the caller will have a reference as to which individual files came from which compressed files. The (I)nventory command is disabled if the (F)lag command is disabled. 4.6 Notes Regarding the (V)iew Command --------------------------------------- Callers may view compressed files inside of the compressed file they are currently viewing. The embedded files must have a recognizable extension of ZIP, ARJ, RAR, LZH or ARC to be (V)iewed. When "V" is entered again (while viewing an -embedded- archive) they are asked if they want to return to the original file. Callers may perform any PCBFV function on the embedded compressed file that they can perform on any other compressed file. PCBFV supports "one-deep" embedded file (V)iewing (for example, a second ZIP file inside the first ZIP file, but not a third ZIP file inside the second ZIP file. -------------------------------------------------------------------- Page 16 PCBFV Page 16 -------------------------------------------------------------------- 4.7 Notes Regarding the (D)elete Command ----------------------------------------- The (D) command allows the local Sysop to delete unwanted files from ZIP and ARJ files (only), such as BBS advertisements, COMMAND.COM, etc. This command can only be used if PCBFV has been started with /L on the command line in PCBFiler, FVMM, or local utility modes. This command is completely disabled whenever a caller is on remotely, including the Sysop. If (D) is entered while on-line, it is not accepted as input (in other words, the D cannot even be typed at the PCBFV prompt). After selecting (D), the local Sysop will be prompted for a filename in the compressed file to delete. PCBFV will then re-display the filename and ask the local Sysop for confirmation. If (D) is entered while viewing a ZIP file which contains ANY files with -AV stamps, or an ARJ 2.41 file with a security stamp, PCBFV will warn the Sysop. Currently, PCBFV only checks for -AV in ZIP files made with PKZIP 1.10, 2.04c, 2.04e and 2.04g, and PCBFV only checks for ARJ security in ARJ files made with ARJ 2.41 (rev 6). If a newer compression utilities become available and are used to create ZIP or ARJ files and the (D) command is used, PCBFV MAY warn that a new compression type has been detected and the -AV test could not be performed. See page 18 section 5.1 for additional details regarding new utilities. Non-ZIP and ARJ compression types may contain "security envelopes". Future versions of PCBFV may be given the ability to detect these "envelopes", thereby allowing the (D) command to function with other compression types in addition to ZIP and ARJ files. The (D)elete command has the same memory and external compression utility requirements as those for ZIP and ARJ (F)lag requirements. 4.8 Notes Regarding the (E)xtra ZIP, ARJ & RAR Information Command ------------------------------------------------------------------- PCBFV will display extra technical data about ZIP, ARJ & RAR files. This extra information includes whether or not member files contain ZIP -AV authenticity stamps, the version or revision of the utility used to compress the member file, whether each member file was compressed in text or binary mode (RAR files will indicate whether the file is locked or not) and the host operating system each member was compressed in (DOS, OS/2, Unix, etc.). NOTE: PCBFV does not check the validity of the ZIP or RAR-AV stamps or ARJ security envelopes. PCBFV only displays whether or not the file has an -AV or security envelope status. NOTE: PCBFV only checks for AV/security markings in ZIP, RAR and ARJ files made with the version of those utilities listed on page 17. If newer versions of the archiver become available and are used to make the file being viewed, the "-AV" column will be blank or may contain incorrect information. See section 5.1 on page 18 for more details regarding new compression utilities. -------------------------------------------------------------------- Page 17 PCBFV Page 17 -------------------------------------------------------------------- 5.0 Required Compression Utilities ----------------------------------- The compression utilities required by PCBFV depend on the types of compressed files carried on your system. Below is a summary of the required files for each compression type, and any limitations PCBFV imposes on them. PCBFV only supports "release" versions from the compression utility authors. "Alpha" and "Beta" TEST versions of the utilities listed below are not supported. All compression utilities must reside in the location specified for "Location of Compression Utilities" in PCBFV.CNF using FVSETUP.EXE. (SFX = Self-Extracting) * ZIP and ZIP SFX (.EXE) files ------------------------------ -NO- external utility is needed to (R)ead ZIP files created by PKZIP version 1.10 through version 2.04g (1990 to current date). If a ZIP file is encountered which was created by PKZIP 1.0 (1989), or if PCBFV detects a newer compression type in a ZIP file, PCBFV will use PKUNZIP to extract the file for (R)eading. -NO- external utility is needed to (F)lag to a FLAG.ZIP file when the currently viewed file is a ZIP file and the FLAG-File is a ZIP file. When the currently viewed file is -not- a ZIP file but the FLAG-File -is- a ZIP file, PKZIP version 2.04g is used to compress the (F)lagged file to the FLAG.ZIP file. * LZH and LZH SFX (.EXE & .COM) files ------------------------------------- LHA.EXE version 2.12 is required to (R)ead and (F)lag -from- .LZH files. LHA.EXE will also be required when (F)lagging -to- a LZH file (FLAG.LZH). * ARJ and ARJ SFX (.EXE) files ------------------------------ ARJ.EXE version 2.50a is required to (R)ead and (F)lag -from- .ARJ files. ARJ.EXE is also required when (F)lagging -to- an ARJ file (FLAG.ARJ). Sysops using ARJ as a FLAG-File should be aware that ARJ requires a large amount of memory to create ARJ files. * RAR and RAR SFX (.EXE) files ------------------------------ UNRAR.EXE version 2.00 is required to (R)ead and (F)lag -from- .RAR files. RAR.EXE version 2.00 is required when (F)lagging -to- a .RAR file (FLAG.RAR). * ARC files ----------- PKUNPAK.EXE version 3.61 is required to (R)ead and (F)lag -from- ARC files. PKPAK.EXE version 3.61 is required when (F)lagging -to- an ARC file (FLAG.ARC). SFX ARC files are not supported by PCBFV. -------------------------------------------------------------------- Page 18 PCBFV Page 18 -------------------------------------------------------------------- 5.1 New Compression Utility Releases ------------------------------------- PCBFV generally does not become obsolete when a new compression method is added to an existing compression utility. If the author of a particular compression utility adds a new compression type, they usually do not change the "headers" in the compressed file. This allows utilities such as PCBFV to view their contents as normal, except for the "compression method", until PCBFV can be updated. PCBFV will display "New\Unk" for the compression method if viewing a file which was created with a compression utility which contains a new compression type. It is recommended that new compression utilities (versions newer than those listed in section 5.0 page 17) NOT be used for PCBFV's (R)ead, (F)lag, etc. commands without checking with Yandell Custom Software first. Newer compression utility releases can and most likely will require more memory than their predecessors, and PCBFV may need to be updated to test for the correct memory requirements. NOTE: PKZIP -AV stamps have changed with each new release of PKZIP since being added to ZIP version 1.1. Any PCBFV functions utilizing -AV information such as (E)xtra should be used with this in mind. NOTE: When a new PKZIP or ARJ is released, the PCBFiler /L mode (D)elete command should not be used until PCBFV can be updated to handle new -AV stamps/security envelopes, or until Yandell Custom Software announces no updates to PCBFV are needed. NOTE: Support for a new version of a supported compression utility is only added to PCBFV when the new version is in "release" and no longer in a "testing phase". PCBFV only supports "release" versions from the compression utility authors. "Alpha" and "Beta" TEST versions of the utilities listed on page 17 are not supported. 5.2 Sysop Function Keys ------------------------ PCBFV follows F3 (printer on/off), F7 (alarm on/off) and F9 (display on/off) toggles from PCBoard. If F3 is on, PCBFV will print any information sent to the caller log to the printer also. If F7 is on, PCBFV will beep locally (usually caller input errors). If F9 is off, PCBFV will turn the screen off. Pressing any key locally turns the screen on if F9 is active. You may toggle these three function keys on or off. Their status will be displayed on the command line in parenthesis (PAB). Note: toggling an option on or off is local to the PCBFV process only. When PCBFV returns control to PCBoard, the toggles will be in the same state as before the File View. Note: the "B" displayed in (PAB) is the F4 page bell indicator. This is shown on PCBFV's status line for information purposes only. -------------------------------------------------------------------- Page 19 PCBFV Page 19 -------------------------------------------------------------------- 5.3 Technical Notes -------------------- PCBFV requires approximately 220K of memory to function properly. To insure enough memory is available, PCBoard MUST be set to swap-out during shells. See section 2.0 on page 5 for instructions. A FOSSIL driver is required if using PCBFV with "PCBoard for OS/2". An OS/2 communications driver often used by PCBoard Sysops is SIO. Many people incorrectly assume SIO by itself is a FOSSIL driver, but it is not. The SIO package -contains- a FOSSIL driver called VX00 which must also be installed with SIO. PCBFV works with non-standard com ports, addresses, and IRQs. COM1 is address 3F8/IRQ 4. COM2 is address 2F8/IRQ 3. If a COM port other than 1 or 2 is used, PCBFV will use the address and IRQ as indicated in PCBOARD.DAT for the node. PCBFV will read the "PCB" environment variable modem settings. When found, these switches override any settings found in PCBOARD.DAT. These switches are: /PORTx /PORTxF /OS /COMx: /BASE:xxx /IRQ:x. Carrier is monitored by PCBFV. Should a caller drop carrier while in PCBFV they will be returned to PCBoard, which will detect the "no carrier" status and cycle appropriately. PCBFV checks for adequate disk space before attempting to extract a file for (R)eading or (F)lagging. PCBFV follows the screen color and intensity as set in PCBSETUP for PCBoard (local screen). If PCBFV swaps and EMS is not available, two files are created in the PCBFV work area called FVSWPxxx.$$$ & FVTMPxxx.$$$ (xxx = node). PCBFV removes PCBoard @X color codes if encountered while (R)eading. PCBFV uses the appropriate language "Y" and "N" (Yes/No) characters if configured in the PCBoard multi-language date file. PCBFV performs signature tests on files not having a file extension of ZIP, ARJ, RAR and LZH. If the files are found to be one of these compression types, they will be viewed appropriately. PCBFV supports PCBoard's /LOCALON network mode with a local status line (like PCBoard's) and suspended function key activity. PCBFV's (R)ead, (L)ist and (B)rief commands may be passed filename specifications, for example L;*.DOC or R;*.TXT. -------------------------------------------------------------------- Page 20 PCBFV Page 20 -------------------------------------------------------------------- 5.4 Error Messages and Solutions --------------------------------- PCBFV displays verbose on-screen installation error messages, such as invalid paths and file-names you may have placed in PCBFV.CNF. The following are explanations of PCBFV's error messages which need more detail than can be displayed in an error message on the screen: * bad command or filename * This is a DOS error message indicating that PCBVIEW.BAT could not run or find PCBFV.EXE. * Error (1) extracting file * The file selected for (R)eading or (F)lagging already existed in the work directory for this node. As a precaution, PCBFV will not overwrite a file which already exists. * Error (2) extracting file * This indicates the file appears in the compressed file but could not be extracted. While using PCBFV in any local mode, use the (W)atch command by pressing "W" at the PCBFV main prompt. This allows you to see the compression utility's screen display and the messages generated by it or the operating system. * Configuration Error (1), (F)lag disabled. * This means you have not placed a valid compressed extension on the FLAG-File name in the FVSETUP "Loc\Name of new flagged file". The file name must contain a valid extension such as .ZIP, ARJ, RAR, LZH or ARC. * Configuration Error (2) * DOS has a limit of 128 characters that can be input as a command. When PCBFV created the command to (R)ead or (F)lag with locations in FVSETUP, the command exceeded the limit. While possible with (R)ead, this occurs mostly with (F)lag where the command line is longer. Shorten the following parameters in FVSETUP: - Work location of extracted file : - Path to compression utilities : - Loc\Name of new (F)lagged file : Since the "Work location of extracted file" parameter is used in the compression utility's command line twice when (F)lagging a file, it can often be the source of the exceeded limit. Shorten the length of the parameters and make the coinciding changes in your directory structure. The "Work location" should be single directories for each node off of the drive's root, for example C:\WORK1, C:\WORK2, etc. * PCBFV Internal ZIP error: ## * Contact the author with the error message, the error number, and upload the ZIP file it occurred with. * FOSSIL driver not found! * Carefully read section 1.3 on page 4. * Error initializing FOSSIL * " " " " " " " While using PCBFV in any local mode, you may use the (W)atch command by pressing "W" at the PCBFV main prompt. This will allow you to see an external compression utility's screen messages and view any error messages generated by them or the operating system. This command has no effect when PCBFV internal ZIP routines are used with ZIP files. The (W)atch command cannot be used when a caller is on-line. -------------------------------------------------------------------- Page 21 PCBFV Page 21 -------------------------------------------------------------------- 5.5 Caller Log Entries ----------------------- PCBFV makes pertinent entries into the caller log as outlined below. When a caller (F)lags a file for separate download: * FILENAME.DOC in FILENAME.ZIP flagged for download When a caller (V)iews an archive inside another archive: * View executed on file (INSIDE.ZIP) from (OUTSIDE.ZIP) PCBFV will make the following entries in the caller log to alert the Sysop if inadequate disk space is encountered: * Insufficient disk space to Read FILENAME.TXT * Insufficient disk space to Flag FILENAME.TXT If the (S)elect command is enabled, PCBFV will make the following entries in the caller log if the corresponding event occurs: * View executed on file (FILENAME.ZIP) * Error executing View of file (FILENAME.ZIP) * (FILENAME.ZIP) not found on disk! * Insufficient security for Viewing (FILENAME.ZIP) * Incorrect View Password for File (FILENAME.ZIP) * (123456789.ZI) is an invalid filename! The caller log entries for the (S)elect command are identical to the corresponding default entries in PCBoard's PCBTEXT. If you do not wish for PCBFV to make these entries to your caller log file(s), this capability may be turned off by using FVSETUP.EXE to disable it. 5.6 Where To Receive Assistance -------------------------------- Yandell Custom Software (YCS) provides the following technical assistance for PCBFV: 813-842-8099 The YCS Support System. Available to all BBS Sysops. INSTANT on-line credit card registration and support system for YCS Shareware. On-line 7 days per week, 24 hours per day. -------------------------------------------------------------------- Page 22 PCBFV Page 22 -------------------------------------------------------------------- 5.7 Disclaimer and Warranty ---------------------------- PCBFV is a shareware product. PCBFV may be uploaded to BBS systems as long as copyright notices are not removed and no changes are made to the program. There are no warranties, expressed or implied, for unregistered copies of PCBFV. Sysops who install PCBFV on their systems assume any and all liabilities for anything which may result as a consequence of running PCBFV. For registered copies of PCBFV, Yandell Custom Software warrants PCBFV will perform as specified in this documentation. In the event that PCBFV does not perform as specified, Yandell Custom Software may elect to fix PCBFV or refund the amount paid, if YCS is notified within 90 days of the initial registration. This notification must contain a description that enables YCS to reproduce the situation. Under no circumstances shall Yandell Custom Software or the author of PCBFV be liable for any loss of profit or any other damages, including but not limited to special, incidental, consequential, or other damages, arising out of the use or inability to use PCBFV. 5.8 License to Use PCBFV ------------------------- PCBFV is not "public domain" or "free" software. A limited license is granted to use and evaluate PCBFV for thirty days after initial installation. PCBFV must be registered if it is used after the initial thirty day evaluation period. A PCBFV registration may be used only on the original licensee's BBS system and only on nodes the original licensee owns and operates for their own purposes. If the original licensee provides some or all of their nodes to another entity, those nodes will require their own PCBFV registration. PCBFV registrations are not transferable. A PCBFV registration is a license to use PCBFV software on one (1) BBS System at a single location with as many nodes as the original licensee owns and operates at that location. When the licensee owns and operates other BBS' in other locations, each location requires a separate PCBFV registration. If PCBFV has not been registered after 30 days, a Sysop reminder will begin appearing at program termination and will also be written to the current node's caller log file. -------------------------------------------------------------------- Page 23 PCBFV Page 23 -------------------------------------------------------------------- 6.0 Registering PCBFV ---------------------- PCBFV is not free software. PCBFV must be registered no later than 30 days after installation. Registration is $20.00 and may be paid by check, money order, VISA, Mastercard, and American Express. Receive a registration number INSTANTLY by registering with a major credit card! Refer to the enclosed file ORDER.FRM for complete registration instructions. 6.1 Register With CONFIDENCE - Author Information -------------------------------------------------- Brent Yandell has been programming for over fourteen years including more than nine years of developing telecommunications software. In 1994 and 1995, Clark Development Company (developers of PCBoard) held a contest for "favorite PCBoard add-ons". PCBFV was a winner in both years, as voted by PCBoard Sysops! Yandell Custom Software (YCS) is a licensed business, operating and existing under the laws of the State of Florida since July, 1990. Writing BBS Shareware doors and utilities, in addition to custom programming, is our business... our ONLY business. First Door Release: 7/6/87 (USBBSDoor). Still updated and supported! YCS Shareware is GUARANTEED (each product's documentation contains each product's specific guarantee). Yandell Custom Software is an *AUTHORIZED* credit card merchant for VISA, Mastercard and American Express charge cards.